<:#1136,9360>The common open software environment process came into being as sixe the initial announcement highlighted specific technology areas, the intent of course, this can be achieved only if the open system industry rallies around thnd the industry through increas
ed growth and innovation in the open system markeconsensus among more vendors.
<:#284,9360>
<:#568,9360>This whitepaper incorporates input from sources throughout the openware industry to continue to improve its competitive postion. Feedback and conve
<:#284,9360>
<:#568,9360>The audience for this whitepaper includes OEM suppliers of open sysis also addressed to existing consortia, which have already made substantial con
<:#284,9360>
<:#568,9360>This whitepaper has five major sections: First, a demonstration of Third, an explanation of how this process would work in practice; Fourth, a setlved.
<:#284,9360>
<:#284,9360>
<:#568,9360>The paper proposes no new organizations. Existing organizations havanizations, except for X/Open, whose specification, certification, and branding
<:#284,9360>
<:#284,9360>This overview section concludes by breaking apart the phrase "common
<:#284,9360>
<:#284,9360><+!>Common.<-!>
<:#568,9360>Users have made it clear that they need system software to be "plugngle supplier or to face a major upheaval if they decide to change suppliers.
<:#284,9360>
<:#568,9360>The common open software environment process will make use of existtions and branding will be used to make this distinction clear.
<:#284,9360>
<:#568,9360>The primary benefits of common specifications for industry standardit of stable, open specifications, they will be drawn to make more and more appl
<:#284,9360>
<:#284,9360><+!>Open.<-!>
<:#852,9360>One important use of "open" applies to the inclusive nature of theftware environment process by the active solicitation from working groups for inary for approving specifications, participants in the common open software envir
<:#284,9360>
<:#1420,9360>A second important use of "open" applies to technology, where it haion of industry standard "open" technology. Under this clarification, a technolo unrestriced (e.g., it is not required to go to any particular supplier for the specification requirements to
two technologies that formerly did not meet this implementation, as long as they pass the necessary tests. Industry standard tecmentations should be licensed readily and equitably to the industry with equal a
<:#284,9360>
<:#284,9360><+!> Software Environment.<-!>
<:#568,9360>Software Environment means defining a standards-based environment fndors that does not limit their software options.
<:#289,9360> <+!>FOUNDATION FOR CUSTOMER CHOICE<-!>
<:#284,9360>
<:#568,9360>With the success of open systems comes an expanding set of specificr future options for choosing a different vendor for another solution.
<:#284,9360>
<:#284,9360>Many vendors in the open software industry are determined to defineganization.
<:#284,9360>
<:#568,9360>Like the companies that recently announced a proposed standard forpete vigorously against each other to sell their own particular product.
<:#284,9360>
<:#284,9360>More specifically, the products that result from the open software p
<:#568,9360>For application developers, common open software products offer ease compatibility they require on systems from different vendors. The efficiency o
<:#284,9360>in improved availability of application titles for end users.
<:#284,9360>
<:#568,9360>For system and network administrators, common open software producte availability of single point multiplatform system management capability.
<:#284,9360>
<:#568,9360>For end users, they bring a consistent look and feel on the desktopcation expense. The common environment will increase the number of available app
<:#284,9360>
<:#568,9360>Finally, system integrators will have available to them more competiencies realized in systems and network administration will be passed on to user
<:#284,9360>
<:#568,9360>Thus all these customer constituencies will be free to select a venon of standards. _______________________________________________________________
<:#284,9360>
<:#289,9360> <+!>ADDING A CATALYST TO THE OPEN SYSTEM PROCESS<-!>
<:#284,9360><+!>
<:#284,9360>Technical innovation and user requirements have traditionally driven
<:#852,9360>1). Companies then competed for customers on the merits of their in facto standards emerged from the choice of users, open system providers have nent of common open software has grown over time.
<:#284,9360>
<:#1420,9360>In an effort to accelerate the availability of open system specificat the point before formal submission of specifications to recognized industry bn submission to the industry standards organization will allow the specification compatible product solutions
while accelerating time to market. A complete specill be licensed and made available readily and equitably to the industry at larg
<:#284,9360>
<:#852,9360>Acting only as a catalyst to the existing open system process, thisr services, have laid a solid foundation for the current acceleration. Their bes should make it easier to form working groups with broader representation than h
<:#289,9360> <+!>HOW THE PROCESS WOULD WORK IN PRACTICE<-!>
<:#284,9360><+!>
<:#568,9360>Central to the above process is achieving consensus to endorse a spels. This section describes how that might work.
<:#284,9360>
<:#289,9360> <+!>Formation of ad hoc working groups.<-!>
<:#852,9360>There are plenty of examples of successful multi-vendor solment spanned memebership of these organizations, and will work with these groupsxisting industry infrastructure evolves to accommodate the breakdown of old barr
<:#284,9360>
<:#568,9360>There is a well-known trade-off between the size of a group and itsof a larger group effort gain broad approval more quickly because the direct inv
<:#284,9360>
<:#1136,9360>The dilemma for the common open software environemnt is to form worthe lead and solicits input from the broader community. Such working groups shou all cases recommendations of these working groups will be submitted for widespr of technology, and is not lim
ited to any specific set of companies.
<:#284,9360>
<:#284,9360><+!> Preparation of formal specification and certification tests.<-!>
<:#568,9360>Each working group is to be charged with producing a detailed formahe certification and branding program would be managed by a neutral industry gro
<:#284,9360>
<:#568,9360>After the specification in finalized by a body such as X/Open, the in a branding program. This body would evaluate the tests and coordinate as appividual vendors can cite conformance.
<:#284,9360>
<:#284,9360>The catalyst added by the common open software environment processentation.
<:#284,9360>
<:#284,9360>
<:#284,9360>
<:#284,9360>
<:#284,9360><+!> Sample implementation.<-!>
<:#852,9360>Implementations of the specification could come to the marketplacee implementations that others could license. Early availability of an implementares a readily licensed sample implementation, available consistently to the indu
<:#284,9360>
<:#289,9360> <+!>Key points of common open software environment process<-!>.
<:#284,9360>There are five key points to the common open software environment pr
<:#284,9360>
<:#284,9360>1) System suppliers come together in a working group to accelerate t
<:#284,9360>
<:#284,9360>2) Each draft specification will be submitted to a recognized indust
<:#284,9360>
<:#284,9360>3) One or more sample implementations should exist for each specific
<:#284,9360>
<:#284,9360>4) Test suites should be available for certification and branding to
<:#284,9360>
<:#284,9360>5) The process allows for different companies to participate for eac
<:#284,7920>
<:#289,7920> <+!>PRINCIPLES OF THE PROCESS<-!>
<:#568,7920>This section describes the acceleration from the point of view of th
<:#284,7920>
<:#284,7920><+!> Contributors.<-!>
<:#568,7920>To demonstrate a commitment to the principles of the common open sof
<:#284,7920>
<:#284,7920> - Accelerate multi-vendor definition of a draft specification ah
<:#284,7920> standards setting organization if necessary, by participating in
<:#284,7920> groups representing a critical mass of the open system industry.
<:#284,7920>
<:#284,7920>
<:#284,7920> - Submit an unencumbered draft specification to an industry revi
<:#284,7920> adoption process, and abide by the decisions of specification re
<:#284,7920>
<:#284,7920> - Ensure their implementation conforms to a rigorous specificati
<:#284,7920> certification, and branding mechanism.
<:#284,7920>
<:#284,7920> - Allow the building of unencumbered (no royalty) common behavio
<:#284,7920> implementations to the specification. (Any necessary patent lice
<:#284,7920> be openly licensable on reasonable terms and conditions consiste
<:#284,7920> standards organization practice.)
<:#284,7920>
<:#284,7920> - Encourage availability for open licensing of a sample implemen
<:#284,7920> certification test suites, including early access to source code
<:#284,7920> rapid deployment.
<:#284,7920>
<:#284,7920> - Compete vigorously against each other on the basis of quality
<:#284,7920> implementation, service, support, price, and other added value.
<:#284,7920>
<:#289,7920> <+!>Vendors.<-!>
<:#1136,7920>This same set of principles can be extended to what vendors of open
<:#284,7920>
<:#284,7920> - That the specification will provide sufficient detail for them
<:#284,7920> implementation from scratch and that if they do so they will ha
<:#284,7920> royalties to pay for use of the specification.
<:#284,7920>
<:#284,7920> - To be able to brand their implementations to the available sp
<:#284,7920> so that their customers know of their compatibility with other
<:#284,7920> vendors.
<:#284,7920>
<:#284,7920> - That vendors, working together or separately on implementation
<:#284,7920> on the open sysetm specification, will be encouraged to make suc
<:#284,7920> implementations available for licensing, including early access.
<:#284,7920>
<:#1420,7920>The principles in this section tend to apply differently during parw to be a full participant in the common open software environment process at al
<:#284,7920> <+!>SOFTWARE LIFE CYCLE AND STAGES OF THE PROCESS<-!>
<:#284,7920>
<:#1136,7920>Software technology passes through roughly four stages in its lifecreases and the value of commonality increases.
<:#284,7920>
<:#568,7920>For the technology that ultimately becomes industry standard, the fo
<:#284,7920>
<:#568,7920>1) Innovation - Vendors market a variety of solutions, often incompa
<:#284,7920>.
<:#568,7920>2) Common Direction - User demand for commonality drives innovative
<:#284,7920>.
<:#568,7920>3) Deployment - Vendors produce a draft specification, show industry
<:#284,7920>
<:#852,7920>4) Availability - Formal approved specification exists and certifica
<:#284,7920>
<:#852,7920>The remainder of this section comments more on each of these stages.
<:#284,7920>
<:#289,7920> <+!>Innovation.<-!>
<:#3408,7920>In the innovative phase, many different solutions may exist and use Users accept a corresponding high risk because the technology may become obsolest meet those needs. Or the technology may be one where a variety of different oin this whitepaper addresses o
nly the software that moves out of the innovative
<:#284,7920>
<:#289,7920> <+!>Common Direction.<-!>
<:#1420,7920>As technology matures, users see the value in, for example, exchangdors may confer to set a common direction, as a catalyst to the open system proc
<:#2840,7920>The common open software environment process allows for any group o it their support, while retaining their ability to address independently the bre from any quarter, often initially through meetings of a few vendors. An actionication.
<:#284,7920>
<:#284,7920>A common direction can take any of several forms:
<:#284,7920>
<:#568,7920>- Vendors could decide to integrate some existing technology and to
<:#284,7920>
<:#284,7920>- Vendors could decide to endorse a de facto standard (e.g., Motif).
<:#284,7920>
<:#568,7920>- Vendors could set up a work group to write a draft specification o
<:#284,7920>
<:#289,7920> <+!>Deployment.<-!>
<:#2556,7920>In technologies where commonality has a critical mass of support, iwriting all components and licensing it to others, to a collection of cooperativovisions for early access of specifications, implementations, and tests to facil
<:#284,7920>
<:#289,7920> <+!>Availablity.<-!>
<:#1988,7920>After a specification is approved and adequate test suites are avaither on the basis of product availability, quality, service, price, and other ad__________________________
<:#284,7920>
<:#284,7920>
<:#284,7920>
<:#284,7920>
<:#284,7920>
<:#284,7920>
<:#289,7920> <+!>CONCLUDING REMARKS<-!>
<:#284,7920>
<:#852,7920>The common open software environment process has been proposed as a
<:#284,7920>
<:#568,7920>The common open software environment process is an open system proce
<:#284,7920>
<:#284,7920>
<:#284,7920>The purpose of this whitepaper is
<:#284,7920>
<:#284,7920> - to lay out the principles for a common open software environme
<:#284,7920> which contributors and vendors cooperate for the growth of the
<:#284,7920> and for the benefit of users, and
<:#284,7920>
<:#284,7920> - To describe a process that embodies this cooperation.
<:#284,7920>
<:#852,7920>Now the task is to build support for these principles and processes.
<:#1704,7920>The body of this paper outlines some principles and strategies fordix proposes a tactical response for several scenarios, with a focus on setting
<:#284,7920>
<:#289,7920> <+!>1. Starting a New Common Direction Activity.<-!>
<:#284,7920>
<:#1136,7920>Suppose your company has some state of the art expertise in a techn environment process?
<:#284,7920>
<:#284,7920>Here are some suggested steps:
<:#284,7920>
<:#568,7920> 1) Test your assessment of the business opportunity and the technol
<:#284,7920> a. Demand for commonality
<:#284,7920> b. Key multi-vendor agreement
<:#284,7920> c. Commitment to open specification
<:#284,7920> d. Availability of sample implementation and tests
<:#284,7920>
<:#852,7920>2) Become familiar with the principles of the common open software
<:#284,7920>
<:#1136,7920>3) Identify and engage other companies. Work with existing workingle.
<:#284,7920>
<:#289,7920> <+!>2. Conducting a Common Direction Setting Activity.<-!>
<:#284,7920>
<:#2272,7920>Suppose there is now a group formed which intends to set a common da technology to a specification that will be widely adopted and implemented. Suce directed at both rapid progress and broad participation.
<:#284,7920>
<:#284,7920>Here are some suggested steps:
<:#284,7920>
<:#568,7920>1) Seek input from companies not included in your small group to be
<:#284,7920>
<:#852,7920>2) Identify an appropriate vendor-neutral standards organization and
<:#284,7920>
<:#1136,7920>3) At an appropriate time make a press announcement citing the comm open software environment process.
<:#284,7920>
<:#852,7920>4) Prepare a draft specification for submission to the selected stan
<:#284,7920>
<:#852,7920>5) Follow through with you implementation of the specification. Enga
<:#284,7920>
<:#284,7920>6) Facilitate broad availability of implementations to the specifica
<:#284,7920>
<:#289,7920> <+!>3. Joining an Existing Direction Setting Activity<-!>.
<:#284,7920>
<:#1988,7920>Suppose a group of companies has made a public announcement of a diou wish to facilitate the adoption of a common direction, and you wish to have ydvantage of it?
<:#284,7920>
<:#284,7920>Here are some suggested steps:
<:#284,7920>
<:#568,7920>1) Contact one or more of the companies that announced the common d
<:#284,7920>
<:#568,7920>2) Make your requirements known to the participants in the common di
<:#284,7920>
<:#1704,7920>3) If your wish to influence the common direction, prepare a positiand recognizing as well that not all proposals can be incorporated. Proposals th
<:#284,7920>
<:#568,7920>4) Seek to be involved in any press releases that come from the comm
<:#284,7920>
<:#852,7920>5) Contact the selected vendor-neutral standards organization and re
<:#284,7920>
<:#852,7920>6) Consider developing a sample implementation, either alone or work
<:#284,7920>
<:#284,7920>
<:#284,7920>
<:#284,7920>
<:#284,7920><+!>4. Other Stages of Software Life Cycle<-!>
<:#284,7920>
<:#1136,7920>This appendix has focused on the setting of common directions, whics well.
